2016-01-18 - 24193 - Service Request - 2016 Order Fulfillment and HR - Week ending Aug 05 #ProductionBreakFix #SDFI #FIMMSD

2016-01-18 - 24193 - Service Request - 2016 Order Fulfillment and HR


Problem Summary

All supporting activities that are less than 4 hours in 2016 are updated in this sheet.

Admin Info


Purpose
 All supporting activities that are less than 4 hours in 2016 are updated in this sheet.
Requested by
 Jeffrey Mau
Issue Date
 08/01/2016 - 08/05/2016
Resolved by
 Surya/Deepak/Mehta/Raghav
Resolved Date
 08/05/2016
Document Status
 Completed

Detailed Problem Description

(Include Screen Shots if required )
Dt 08/01/2016

Issue #1: For SO 3256367, the customer submitted for 60 units. The 60 units that are tied to the order are coming in for different dates on Global PO’s, but the ATP for all of the units in the order are automatically defaulted to the latest ATP (as opposed to splitting the line).

Dt: 08/03/2016

Issue#2: Odd pricing for certain Japan call offs, There are two J3AP values, the first of which say it is inactive,
However, the ZJBA condition is reducing the value by 3,600 JPY, even though the percentage is 50%, even though one of the J3APs is inactive, it is taking the base value as 7,200.


Japan-Calloff.png

Japan Calloff2.png

Japan Calloff3.png


Dt: 08/03/2016 (JPN Pricing issue of Dt: 08/03/2016)

Newera got a response from SAP stating to maintain routine 495 in the calculation type of ZJBA in the procedure which will eventually force the the condition to take up the active J3AP into account for validation,
Newera approached BMS for furtther assistance reg. the same.

Solution Analysis and Recommendation

(Include Screen Shots if required)
BMS Suggestion for Issue #1:

The usage in the SO is ZCL/ZCD , then as per the order scheduling there won’t be any size spilt and all the units in the order are automatically defaulted to the latest ATP.
The Order #3256367 is ZCD order and so all the 60 units are confirmed to latest ATP date without any split.

SS-1.png

SS-2.png
SS-3.png

BMS Suggestion for Issue #2:
The order was created manually but not sure how two J3AP conditions appeared on the SO. The SO item was created with reference to contract and there was no pricing issue on the contract.
The condition details don’t point to manual entry on either of them and also multiple condition records didn’t exist.
We are not able to replicate the issue as we are not sure of how a duplicate record could be entered w/o manual option.
This is a fit case to raise an OSS.

Resolution

issue#1 Solution is implemented by Newera.

Issue #2 sent to SAP for further assistance and received guidance from SAP, the proposed solution (routine) has been tested in D and noticed weird pricing
The list price seem to be calculating (addition) the price and discount ignoring the minus. The Net Price though is calculated correctly. This could be due to the pricing set up

495-Routine test.png

BMS suggested that before making a decision to change the pricing procedure with the routine, to know how two J3AP conditions appeared on the SO because they were not there on the contract and the SO was created manually.

Release Information

Provide link here to Release Notes if Technical Objects were changed